Your data has issues
There is a problem
- 1000 entries must have valid geometry
| Reference | Name | Tree preservation order | Uprn | Address text | Point | Geometry | Notes | Felled date | Entry date | Start date | End date |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 851 | Mar-82 | 217029319 | ELM PARK ROAD |
POINT (-0.17678 51.4862) Unexpected geom type |
2025-01-03 | ||||||
| 852 | Jul-89 | 217029411 | ELM PARK ROAD |
POINT (-0.17461 51.48699) Unexpected geom type |
2025-01-03 | ||||||
| 853 | Jul-92 | 217029309 | ELM PARK ROAD |
POINT (-0.17686 51.48618) Unexpected geom type |
2025-01-03 | ||||||
| 854 | 13/92 | 217029271 | ELM PARK ROAD |
POINT (-0.17814 51.48562) Unexpected geom type |
2025-01-03 | ||||||
| 855 | Feb-93 | 217029257 | ELM PARK ROAD |
POINT (-0.17843 51.48591) Unexpected geom type |
2025-01-03 | ||||||
| 856 | 30/96 | 217029417 | ELM PLACE |
POINT (-0.17684 51.48906) Unexpected geom type |
2025-01-03 | ||||||
| 857 | K71 | 217029427 | ELM PLACE |
POINT (-0.17693 51.48952) Unexpected geom type |
2025-01-03 | ||||||
| 858 | K71 | 217029429 | ELM PLACE |
POINT (-0.17676 51.4894) Unexpected geom type |
2025-01-03 | ||||||
| 859 | K71 | 217029431 | ELM PLACE |
POINT (-0.17662 51.4893) Unexpected geom type |
2025-01-03 | ||||||
| 860 | Nov-73 | 217029414 | ELM PLACE |
POINT (-0.17661 51.48895) Unexpected geom type |
2025-01-03 | ||||||
| 861 | Nov-73 | 217029418 | ELM PLACE |
POINT (-0.17697 51.48919) Unexpected geom type |
2025-01-03 | ||||||
| 862 | Nov-73 | 217029423 | ELM PLACE |
POINT (-0.17737 51.48944) Unexpected geom type |
2025-01-03 | ||||||
| 863 | Nov-73 | 217029425 | ELM PLACE |
POINT (-0.17755 51.48951) Unexpected geom type |
2025-01-03 | ||||||
| 864 | Nov-73 | 217029427 | ELM PLACE |
POINT (-0.17693 51.48952) Unexpected geom type |
2025-01-03 | ||||||
| 865 | K6 | 217029433 | ELSHAM ROAD |
POINT (-0.21137 51.50043) Unexpected geom type |
2025-01-03 | ||||||
| 866 | K6 | 217029438 | ELSHAM ROAD |
POINT (-0.21144 51.50048) Unexpected geom type |
2025-01-03 | ||||||
| 867 | K6 | 217029444 | ELSHAM ROAD |
POINT (-0.21149 51.50051) Unexpected geom type |
2025-01-03 | ||||||
| 868 | K6 | 217029469 | ELSHAM ROAD |
POINT (-0.21166 51.50065) Unexpected geom type |
2025-01-03 | ||||||
| 869 | K6 | 217029490 | ELSHAM ROAD |
POINT (-0.2119 51.50082) Unexpected geom type |
2025-01-03 | ||||||
| 870 | K6 | 217029491 | ELSHAM ROAD |
POINT (-0.212 51.50088) Unexpected geom type |
2025-01-03 | ||||||
| 871 | K6 | 217029504 | ELSHAM ROAD |
POINT (-0.21219 51.50103) Unexpected geom type |
2025-01-03 | ||||||
| 872 | K6 | 217029516 | ELSHAM ROAD |
POINT (-0.21232 51.50111) Unexpected geom type |
2025-01-03 | ||||||
| 873 | K6 | 217029599 | ELSHAM ROAD |
POINT (-0.21319 51.50175) Unexpected geom type |
2025-01-03 | ||||||
| 874 | K6 | 217029610 | ELSHAM ROAD |
POINT (-0.2133 51.50184) Unexpected geom type |
2025-01-03 | ||||||
| 875 | K6 | 217029646 | ELSHAM ROAD |
POINT (-0.21368 51.50213) Unexpected geom type |
2025-01-03 | ||||||
| 876 | K6 | 217029530 | ELSHAM ROAD |
POINT (-0.21244 51.50121) Unexpected geom type |
2025-01-03 | ||||||
| 877 | K6 | 217029688 | ELSHAM ROAD |
POINT (-0.21465 51.50223) Unexpected geom type |
2025-01-03 | ||||||
| 878 | K6 | 217029775 | ELSHAM ROAD |
POINT (-0.21367 51.5015) Unexpected geom type |
2025-01-03 | ||||||
| 879 | K6 | 217029799 | ELSHAM ROAD |
POINT (-0.21348 51.50135) Unexpected geom type |
2025-01-03 | ||||||
| 880 | K6 | 217029828 | ELSHAM ROAD |
POINT (-0.2131 51.5011) Unexpected geom type |
2025-01-03 | ||||||
| 881 | K6 | 217029836 | ELSHAM ROAD |
POINT (-0.21304 51.50104) Unexpected geom type |
2025-01-03 | ||||||
| 882 | K6 | 217029848 | ELSHAM ROAD |
POINT (-0.21289 51.50092) Unexpected geom type |
2025-01-03 | ||||||
| 883 | K6 | 217029854 | ELSHAM ROAD |
POINT (-0.2128 51.50086) Unexpected geom type |
2025-01-03 | ||||||
| 884 | K6 | 217029866 | ELSHAM ROAD |
POINT (-0.21268 51.50074) Unexpected geom type |
2025-01-03 | ||||||
| 885 | K6 | 217029871 | ELSHAM ROAD |
POINT (-0.21261 51.50069) Unexpected geom type |
2025-01-03 | ||||||
| 886 | K6 | 217029903 | ELSHAM ROAD |
POINT (-0.21223 51.50041) Unexpected geom type |
2025-01-03 | ||||||
| 887 | K6 | 217029916 | ELSHAM ROAD |
POINT (-0.2121 51.50033) Unexpected geom type |
2025-01-03 | ||||||
| 888 | K6 | 217029929 | ELSHAM ROAD |
POINT (-0.21199 51.50024) Unexpected geom type |
2025-01-03 | ||||||
| 889 | Dec-75 | 217029459 | ELSHAM ROAD |
POINT (-0.2116 51.50061) Unexpected geom type |
2025-01-03 | ||||||
| 890 | 16/78 | 217029822 | ELSHAM ROAD |
POINT (-0.21321 51.50117) Unexpected geom type |
2025-01-03 | ||||||
| 891 | Mar-92 | 217029877 | ELSHAM ROAD |
POINT (-0.21252 51.50063) Unexpected geom type |
2025-01-03 | ||||||
| 892 | 44/95 | 217029727 | ELSHAM ROAD |
POINT (-0.21416 51.50189) Unexpected geom type |
2025-01-03 | ||||||
| 893 | Jul-74 | 217030635 | EMBANKMENT GARDENS |
POINT (-0.15777 51.48488) Unexpected geom type |
2025-01-03 | ||||||
| 894 | Jun-78 | 217111636 | EMPEROR'S GATE |
POINT (-0.18609 51.49587) Unexpected geom type |
2025-01-03 | ||||||
| 895 | Jan-86 | 217108416 | EMPEROR'S GATE |
POINT (-0.18573 51.49623) Unexpected geom type |
2025-01-03 | ||||||
| 896 | Jul-72 | 217030917 | ESSEX VILLAS |
POINT (-0.19782 51.50111) Unexpected geom type |
2025-01-03 | ||||||
| 897 | Jul-72 | 217030933 | ESSEX VILLAS |
POINT (-0.19738 51.50091) Unexpected geom type |
2025-01-03 | ||||||
| 898 | Jul-72 | 217030934 | ESSEX VILLAS |
POINT (-0.19727 51.50095) Unexpected geom type |
2025-01-03 | ||||||
| 899 | Jul-72 | 217030935 | ESSEX VILLAS |
POINT (-0.19714 51.501) Unexpected geom type |
2025-01-03 | ||||||
| 900 | K47 | 217107411 | EVELYN GARDENS |
POINT (-0.17865 51.48876) Unexpected geom type |
2025-01-03 |
Showing rows 851 to 900 of 1000
How to fix this issue
Your data is missing a geometry.
The tree guidance explains how to fix the issue:
geometry
The boundary of the tree as a single polygon or multipolygon value. All points in the polygon must be in the WGS84 coordinate reference system.
If you’re providing geometry in a CSV, geometry should be in well-known text (WKT).
You must provide a point or geometry for each tree. You may provide both.
Example: MULTIPOLYGON (((1.188829 51.23478,1.188376 51.234909,1.188381 51.234917,1.187912 51.235022...
If you’re providing geometry in a GeoJSON, GML or Geopackage, use the associated geometry format.
How to improve Royal Borough of Kensington and Chelsea’s data
- Fix the errors indicated
- Use the check service to make sure the data meets the standard
- Publish the updated data on the endpoint URL